Disabling Access Point Notifications

ABSTRACT

Disabling wireless access point notifications is described. In some implementations, wireless access point notifications on a mobile device can be disabled when movement of the mobile device is detected. In some implementations, wireless access point notifications on a mobile device can be re-enabled when the mobile device detects that the mobile device has been stationary for a specified period of time following movement of the mobile device. In some implementations, wireless access point notifications can be disabled on a per access point basis.

TECHNICAL FIELD

The disclosure generally relates to wireless network detection.

BACKGROUND

Modern mobile computing devices are capable of detecting and connectingto wireless access points for accessing networks, including theinternet. These computing devices often provide notifications (e.g.,dialog boxes, pop-up windows, etc.) to users when access points aredetected. Wireless access point notifications are often displayed toprovide the user of the mobile device with a convenient way to identifyand connect to wireless access points. However, in some circumstances,wireless access point notifications can be inconvenient and caninterfere with the use of mobile computing devices.

SUMMARY

Disabling wireless access point notifications is described. In someimplementations, wireless access point notifications on a mobile devicecan be disabled when movement of the mobile device is detected. In someimplementations, wireless access point notifications on a mobile devicecan be re-enabled when the mobile device detects that the mobile devicehas been stationary for a specified period of time following movement ofthe mobile device. In some implementations, movement of the mobiledevice can be detected based on the strength of wireless access pointsignals received at the mobile device. In some implementations, movementof the mobile device can be detected based on global positioning systemdata, motion sensor data, cell tower triangulation, or any other type oflocation and/or movement determining mechanism.

In some implementations, wireless access point notifications can bedisabled on a per access point basis. For example, a user can interactwith a wireless access point notification to indicate a wireless accesspoint for which future wireless access point notifications should bedisabled.

Particular implementations provide at least the following advantages:wireless access point notifications are dynamically and automaticallydisabled; wireless access point notifications are prevented fromdisplaying at inconvenient or inappropriate times.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example of a mobile device moving between wirelessaccess points.

FIG. 2 a flow diagram of an example process for disabling wirelessaccess point notifications.

FIGS. 3A and 3B illustrate example interfaces for disabling individualwireless access point notifications.

FIG. 4 is flow diagram of an example process for disabling individualwireless access point notifications.

FIG. 5 is a flow diagram of an example process for preventing wirelessaccess point notifications.

FIG. 6 is a block diagram of an exemplary system architectureimplementing the features and processes of FIGS. 1-5.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION Automatically Disabling Notifications

FIG. 1 illustrates an example of a mobile device 108 moving betweenwireless access points 102, 104 and 106 on a city grid 100. For example,mobile device 108 (e.g., a cell phone, smartphone, laptop, etc.) can bemoved along path 130. Mobile device 108 can be carried on a person ortransported in a vehicle, for example. As mobile device 108 moves alongpath 130 (e.g., along a street or sidewalk), mobile device 108 candetect wireless access points 102, 104, 106. For example, wirelessaccess points 102, 104 and 106 can correspond to wireless access pointsprovided my various businesses, such as coffee houses, restaurants,bookstores, etc., that mobile device 108 may pass as it travels alongpath 130.

In some implementations, when mobile device 108 detects a wirelessaccess point, mobile device 108 can present a wireless access pointnotification. For example, mobile device can display a window or dialogbox on a display that indicates that a wireless access point has beendetected and identifies (e.g., by name) the wireless access point to theuser. In some implementations, the user can provide input to mobiledevice 108 (e.g., through the displayed wireless access pointnotification) to cause mobile device 108 to connect, join or associatewith the detected wireless access point.

Sometimes, however, a user may not want to connect to wireless accesspoints while the user, and mobile device 108, is moving. For example, auser may be riding in a moving car. The speed at which the car istraveling may not allow for mobile device 108 to stay in range of astationary wireless access point (e.g., wireless access points 102, 104,106) for long enough to access data through the wireless access point.For example, by the time the moving mobile device 108 connects to thewireless access point, mobile device 108 may be moving out of range ofthe wireless access point and be forced to disconnect from the wirelessaccess point.

Moreover, a user of mobile device 108 may be using mobile device 108while mobile device 108 is moving. For example, a passenger in a movingcar may be using a feature or application of mobile device 108. If thepassenger/user is repeatedly interrupted by wireless access pointnotifications while using mobile device 108, the user may get annoyed orfrustrated by the interruptions. For example, as mobile device 108 movesfrom location 110, to location 116, to location 118, to location 120,the mobile device can detect three wireless access points 102, 104, 106and present three wireless access point notifications. If a user isusing mobile device 108 as the mobile device moves from location 110 tolocation 120, the user will be interrupted with wireless access pointnotifications three times even though mobile device 108 may not staywithin range of any wireless access point for long enough to use thewireless access point.

In some implementations, wireless access point notifications on mobiledevice 108 can be automatically disabled while mobile device 108 ismoving. For example, wireless access point notifications can be disabledwhen mobile device 108 is moving so that wireless access pointnotifications will not be presented when a user is unlikely to joindetected wireless access points.

In some implementations, movement of mobile device 108 can be detectedbased on the strength of the signal received from a wireless accesspoint. For example, mobile device 108 can receive signals from wirelessaccess point 102 at locations 110, 112, and 114. At each of thelocations 110, 112 and 114 the signal strength of the signal receivedfrom wireless access point 102 can change or can have differentstrengths. For example, the signal strength of the signal received fromwireless access point 102 at location 110 can be weaker than the signalstrength at location 112. The signal strength of the signal receivedfrom wireless access point 102 at location 114 can be weaker than thestrength of the signal received at location 112 and weaker than thesignal received at location 110. In some implementations, movement ofmobile device 108 can be determined based on the strength of the signalreceived from a wireless access point over a period of time. Forexample, if the signal strength of a signal from wireless access point102 received at mobile device 108 is weak at first, then becomesstronger, then becomes weaker, mobile device 108 is likely movingrelative to wireless access point 102. The gradual increase in signalstrength from location 110 to location 112 can indicate that mobiledevice 108 is moving closer to wireless access point 102. The gradualdecrease in signal strength from location 112 to location 114 canindicate that mobile device 108 is moving away from wireless accesspoint 102.

In some implementations, wireless access point notifications for mobiledevice 108 can be enabled once mobile device 108 has stopped moving orhas become stationary. For example, if a user carrying mobile device 108stops at a coffee shop that provides wireless access point 104, the usermay be more likely to want to connect to the coffee shop's wirelessaccess point 104. Thus, mobile device 108 can be configured to presentwireless access point notifications once mobile device 108 has stoppedmoving.

In some implementations, wireless access point notifications for mobiledevice 108 can be enabled once mobile device 108 has stopped moving fora configured or specified period of time. For example, if mobile device108 is moving in a car and the car temporarily stops at a stop light,the user of mobile device 108 is not likely to want to connect to anywireless access points because the car is going to start moving againonce the stop light turns green. To prevent presenting notificationsduring short pauses in movement, mobile device 108 can be configured toenable wireless access point notifications only after mobile device 108has stopped moving for a configured period of time (e.g., three minutes,five minutes, the duration of a stop light, etc.).

FIG. 2 a flow diagram of an example process 200 for disabling wirelessaccess point notifications. In some implementations, wireless accesspoint notifications on a mobile device configured to present wirelessaccess point notifications can be automatically disabled based ondetected movement of the mobile device. In some implementations,wireless access point notifications on a mobile device can beautomatically enabled based on determining that the mobile device hasstopped moving.

At step 202, a wireless access point is detected at a mobile device. Forexample, the wireless access point can be detected by wirelesscommunication subsystem 624 of FIG. 6.

At step 204, a determination is made whether the mobile device ismoving. In some implementations, the determination is made based inwireless access point signal strengths, as described above. In someimplementations, the determination is made based on global positioningsystem data, movement sensor data (e.g., accelerometer data), and/orbased on location triangulation techniques using signals transmittedfrom cell towers, wireless access points, or other transmission sources.

At step 206, wireless access point notifications on the mobile devicecan be disabled when the mobile device is moving. In someimplementations, when mobile device 108 determines that mobile device108 is moving, wireless access point notifications can be disabled onmobile device 108. For example, wireless access point notificationpopups, windows, dialog boxes, etc. can be prevented from displaying onmobile device 108 while mobile device 108 is moving.

At step 208, wireless access point notifications can be enabled(re-enabled) on the mobile device when the mobile device has stoppedmoving. In some implementations, mobile device 108 can determine whenmobile device 108 has stopped moving. For example, the same techniquesfor detecting movement described at step 204 can be used to determinewhen mobile device 108 has stopped moving. In some implementations,mobile device 108 can determine when mobile device 108 has stoppedmoving for a configured period of time. For example, mobile device 108can store data indicating a period of time that the mobile device needsto be stationary before wireless access points are enabled on mobiledevice 108. Once mobile device 108 determines that mobile device 108 hasstopped moving, mobile device 108 can wait the configured period of timebefore enabling wireless access point notifications on mobile device108.

Manually Disabling Individual Notifications

FIG. 3A illustrates example interface 300 for disabling individualwireless access point notifications. For example, a mobile device can beconfigured to present wireless access point notifications when themobile device detects a wireless access point. In some implementations,detected wireless access points can be displayed on interface 300. Forexample, interface 300 can present graphical elements 302, 304, 306 and308 on interface 300 for displaying information related to detectedwireless access points. For example, graphical elements 302-308 can eachbe associated with a corresponding wireless access point and presentinformation for the wireless access point, such as display namesassociated with wireless access points, security information (e.g.,encryption algorithms, password requirements, etc.), and signalstrength.

In some implementations, a user can interact with graphical elements302-308 to disable wireless access point notifications for particularwireless access points. For example, if interface 300 is presented on atouch-sensitive display (e.g., touch screen 646 of FIG. 6), a user mayslide a finger along graphical element 308 as indicated by dashed line310 to cause graphical element 312 to display. In some implementations,graphical element 312 can be selected by a user to disable wirelessaccess point notifications for the wireless access point associated withgraphical element 308. For example, when a user selects graphicalelement 312, information can be stored on the mobile device thatindicates that wireless access point notification should not bepresented when the wireless access point corresponding to graphicalelement 308 is detected in the future.

In some implementations, a user can select graphical element 312 topresent options for the wireless access point corresponding to graphicalelement 304. For example, if a user selects graphical element 312,interface 350 can be displayed on the mobile device.

FIG. 3B illustrates example interface 350 for disabling individualwireless access point notifications. In some implementations, a user canprovide input to interface 350 to disable wireless access pointnotifications for the wireless access point associated with userinterface 350. In some implementations, a user can select graphicalelement 352 to disable future wireless access point notifications forthe wireless access point associated with interface 350.

In some implementations, a user can input authentication informationinto graphical element 354. For example, some wireless access points canrequire a user or device to be authorized to access the wireless accesspoint. A user can provide authentication information (e.g., a password,key, etc.) through graphical element 354. Once the user has provided theauthentication information, the user can select graphical element 356 tojoin or connect to the wireless access point. If a user does not want toconnect to the wireless access point, the user can select graphicalelement 358 to close interface 350 without connecting to the wirelessaccess point.

FIG. 4 is flow diagram of an example process for disabling individualwireless access point notifications. At step 402, a wireless accesspoint is detected at a mobile device. For example, wirelesscommunication subsystem 624 of FIG. 6 can detect wireless access pointsthat are reachable by the mobile device.

At step 404, a wireless access point notification is presented. Forexample, in response to detecting wireless access points, the mobiledevice can present a wireless access point notification identifying someor all of the wireless access points that are reachable by the mobiledevice. The wireless access point notification can also provideinformation identifying the wireless access point, indicating thestrength of the signal received from the wireless access point and/orauthentication requirements.

At step 406, input is received to disable future notifications for awireless access point. For example, a user can disable future wirelessaccess point notifications for selected wireless access points, asdescribed above with reference to FIGS. 3A and 3B.

At step 408, wireless access point information can be stored fordisabled wireless access points. For example, the mobile device canmaintain a database (e.g., access point notification database 674 ofFIG. 6) of wireless access points for which a user has disabled futurewireless access point notifications. In some implementations, when inputis received from a user indicating that the user does not wish toreceive future wireless access point notifications for a particularwireless access point, identification information for the particularwireless access point (e.g., a name, service set identifier (SSID),media access control (MAC) address, etc.) can be stored in the database.For example, the database can be referenced when wireless access pointsare detected to determine which wireless access points should generatewireless access point notifications.

FIG. 5 is a flow diagram of an example process 500 for preventingwireless access point notifications. At step 502, wireless access pointsare detected at a mobile device. For example, wireless communicationsubsystem 624 of FIG. 6 can detect wireless access points that arereachable by the mobile device.

At step 504, the mobile device can determine if notifications for thedetected wireless access points are disabled. In some implementations,mobile device can compare information associated with the detectedwireless access points (e.g., names, SSIDs, MAC addresses, etc.) toinformation stored in a wireless access point database to determine ifwireless access point notifications are disabled for the detectedwireless access points. For example, if a detected wireless access pointis identified in the database or if the database indicates thatnotifications for the detected wireless access point have been disabled,then wireless access point notifications should not be generated for thedetected wireless access point.

At step 506, the mobile device can prevent wireless access pointnotifications from being presented for identified wireless accesspoints. For example, if step 504 determines that notifications for adetected wireless access point were disabled, then a wireless accesspoint notification will not be generated for the detected wirelessaccess point. In some implementations, wireless access pointnotifications can be generated for some detected wireless access pointsand not for other detected wireless access points. For example, adetected wireless access point for which notifications were disabledwill not appear in the listing of wireless access points on interface 3Awhile a detected wireless access point for which notifications were notdisabled may generate a wireless access point notification and appear inthe wireless access point listing of interface 300.

Example Mobile Device Architecture

FIG. 6 is a block diagram 600 of an example implementation of the mobiledevice 100 of FIGS. 1-5. The mobile device 100 can include a memoryinterface 602, one or more data processors, image processors and/orcentral processing units 604, and a peripherals interface 606. Thememory interface 602, the one or more processors 604 and/or theperipherals interface 606 can be separate components or can beintegrated in one or more integrated circuits. The various components inthe mobile device 100 can be coupled by one or more communication busesor signal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 606 to facilitate multiple functionalities. For example, amotion sensor 610, a light sensor 612, and a proximity sensor 614 can becoupled to the peripherals interface 606 to facilitate orientation,lighting, and proximity functions. Other sensors 616 can also beconnected to the peripherals interface 606, such as a positioning system(e.g., GPS receiver), a temperature sensor, a biometric sensor, or othersensing device, to facilitate related functionalities.

A camera subsystem 620 and an optical sensor 622, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips. The camera subsystem 620 and theoptical sensor 622 can be used to collect images of a user to be usedduring authentication of a user, e.g., by performing facial recognitionanalysis.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 624, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 624 can depend on the communication network(s)over which the mobile device 100 is intended to operate. For example, amobile device 100 can include communication subsystems 624 designed tooperate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi orWiMax network, and a Bluetooth™ network. In particular, the wirelesscommunication subsystems 624 can include hosting protocols such that thedevice 100 can be configured as a base station for other wirelessdevices. In some implementations, wireless communication subsystem candetect wireless access points, detect signal strengths of wirelessaccess points and support other features described with reference toFIGS. 1-5.

An audio subsystem 626 can be coupled to a speaker 628 and a microphone630 to facilitate voice-enabled functions, such as speaker recognition,voice replication, digital recording, and telephony functions. The I/Osubsystem 640 can include a touch screen controller 642 and/or otherinput controller(s) 644. The touch-screen controller 642 can be coupledto a touch screen 646. The touch screen 646 and touch screen controller642 can, for example, detect contact and movement or break thereof usingany of a plurality of touch sensitivity technologies, including but notlimited to capacitive, resistive, infrared, and surface acoustic wavetechnologies, as well as other proximity sensor arrays or other elementsfor determining one or more points of contact with the touch screen 646.

The other input controller(s) 644 can be coupled to other input/controldevices 648, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 628 and/or the microphone 630.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch screen 646; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the mobile device 100 on or off. Pressing the button for athird duration can activate a voice control, or voice command, modulethat enables the user to speak commands into the microphone 630 to causethe device to execute the spoken command. The user can customize afunctionality of one or more of the buttons. The touch screen 646 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the mobile device 100 can present recordedaudio and/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the mobile device 100 can include the functionality ofan MP3 player, such as an iPod™. The mobile device 100 can, therefore,include a 36-pin connector that is compatible with the iPod. Otherinput/output and control devices can also be used.

The memory interface 602 can be coupled to memory 650. The memory 650can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 650can store an operating system 652, such as Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 652 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 652 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 652 can includeinstructions for performing voice authentication. For example, operatingsystem 652 can implement the features as described with reference toFIGS. 1-5.

The memory 650 can also store communication instructions 654 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 650 can includegraphical user interface instructions 656 to facilitate graphic userinterface processing; sensor processing instructions 658 to facilitatesensor-related processing and functions; phone instructions 660 tofacilitate phone-related processes and functions; electronic messaginginstructions 662 to facilitate electronic-messaging related processesand functions; web browsing instructions 664 to facilitate webbrowsing-related processes and functions; media processing instructions666 to facilitate media processing-related processes and functions;GPS/Navigation instructions 668 to facilitate GPS and navigation-relatedprocesses and instructions; and/or camera instructions 670 to facilitatecamera-related processes and functions.

The memory 650 can store access point (AP) notification instructions 672to facilitate the processes and functions described with reference toFIGS. 1-5. For example, the software instructions can includeinstructions for performing voice authentication on a per application orper feature basis and for allowing a user to configure authenticationrequirements of each application or feature available on device 100.Memory 650 can store an access point notification database for storinginformation related to access points, such as the access pointnotification information stored and used with respect to the processesdescribed with reference to FIGS. 1-5.

The memory 650 can also store other software instructions (not shown),such as web video instructions to facilitate web video-related processesand functions; and/or web shopping instructions to facilitate webshopping-related processes and functions. In some implementations, themedia processing instructions 666 are divided into audio processinginstructions and video processing instructions to facilitate audioprocessing-related processes and functions and video processing-relatedprocesses and functions, respectively.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 650 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the mobile device 100 can be implemented in hardware and/orin software, including in one or more signal processing and/orapplication specific integrated circuits.

What is claimed is: 1-21. (canceled)
 22. A method comprising: by amobile device: determining whether the mobile device has been stationaryfor a configured period of time; detecting a wireless access point;causing a wireless access point notification to be presented for thewireless access point as a graphical object on a display of the mobiledevice; and receiving input to the graphical object to disable futurewireless access point notifications.
 23. The method of claim 22, whereinreceiving input to the graphical object to disable future wirelessaccess point notifications comprises receiving input to the graphicalobject to disable future wireless access point notifications for thewireless access point.
 24. The method of claim 23, further comprising:storing wireless access point information indicating that wirelessaccess point notifications are disabled for the wireless access point.25. The method of claim 23, further comprising: causing a list ofavailable wireless access points to be presented on a display of themobile device, wherein the list of available wireless access pointsexcludes the wireless access point for which future wireless accesspoint notifications have been disabled.
 26. The method of claim 22,wherein the presented wireless access point notification indicates thata respective wireless access point has been wirelessly detected andidentifies the respective wireless access point.
 27. The method of claim22, further comprising: disabling wireless access point notifications inresponse to receiving the input to the graphical object, wherein one ormore other user interface features remain enabled while the wirelessaccess point notifications are disabled.
 28. The method of claim 22,further comprising: detecting whether access point notifications havebeen disabled, wherein the causing a wireless access point notificationto be presented is in response to detecting that access pointnotifications have not been disabled.
 29. A non-transitorycomputer-readable medium storing software instructions executable by aprocessor of a mobile device to cause the mobile device to: determinewhether the mobile device has been stationary for a configured period oftime; detect a wireless access point; cause a wireless access pointnotification to be presented for the wireless access point as agraphical object on a display of the mobile device; and receive input tothe graphical object to disable future wireless access pointnotifications.
 30. The non-transitory computer-readable medium of claim29, wherein, in receiving input to the graphical object to disablefuture wireless access point notifications, the software instructionsare further executable to cause the mobile device to receive input tothe graphical object to disable future wireless access pointnotifications for the wireless access point.
 31. The non-transitorycomputer-readable medium of claim 30, wherein the software instructionsare further executable to cause the mobile device to: store wirelessaccess point information indicating that wireless access pointnotifications are disabled for the wireless access point.
 32. Thenon-transitory computer-readable medium of claim 30, wherein thesoftware instructions are further executable to cause the mobile deviceto: cause a list of available wireless access points to be presented ona display of the mobile device, wherein the list of available wirelessaccess points excludes the wireless access point for which futurewireless access point notifications have been disabled.
 33. Thenon-transitory computer-readable medium of claim 29, wherein thepresented wireless access point notification indicates that a respectivewireless access point has been wirelessly detected and identifies therespective wireless access point.
 34. The non-transitorycomputer-readable medium of claim 29, wherein the software instructionsare further executable to cause the mobile device to: disable wirelessaccess point notifications in response to receiving the input to thegraphical object, wherein one or more other user interface featuresremain enabled while the wireless access point notifications aredisabled.
 35. The non-transitory computer-readable medium of claim 29,wherein the software instructions are further executable to cause themobile device to: detect whether access point notifications have beendisabled, wherein the causing a wireless access point notification to bepresented is in response to detecting that access point notificationshave not been disabled.
 36. A mobile device comprising: wirelesscommunication circuitry; a touch-screen; at least one processor; and amemory storing software instructions executable by the at least oneprocessor to cause the mobile device to: determine whether the mobiledevice has been stationary for a configured period of time; detect awireless access point; cause a wireless access point notification to bepresented for the wireless access point as a graphical object on thetouch-screen; and receive input to the graphical object presented on thetouch-screen to disable future wireless access point notifications. 37.The mobile device of claim 36, wherein, in receiving input to thegraphical object to disable future wireless access point notifications,the software instructions are further executable to cause the mobiledevice to receive input to the graphical object to disable futurewireless access point notifications for the wireless access point. 38.The mobile device of claim 37, wherein the software instructions arefurther executable to cause the mobile device to: store wireless accesspoint information indicating that wireless access point notificationsare disabled for the wireless access point.
 39. The mobile device ofclaim 37, wherein the software instructions are further executable tocause the mobile device to: cause a list of available wireless accesspoints to be presented on the touch-screen, wherein the list ofavailable wireless access points excludes the wireless access point forwhich future wireless access point notifications have been disabled. 40.The mobile device of claim 36, wherein the presented wireless accesspoint notification indicates that a respective wireless access point hasbeen wirelessly detected and identifies the respective wireless accesspoint.
 41. The mobile device of claim 36, wherein the softwareinstructions are further executable to cause the mobile device to:disable wireless access point notifications in response to receiving theinput to the graphical object, wherein one or more other user interfacefeatures remain enabled while the wireless access point notificationsare disabled.